User experience enhancements for controlling a group communication

ABSTRACT

User experience enhancements for conducting group communication sessions may include displaying visual feedback on a display to indicate a state of a group communication session. Embodiments may include displaying a quick contact group communication shortcut icon on a home screen of a wireless communication device display, displaying a group communication button in association with the quick contact group communication shortcut icon on the home screen of the display, detecting a selection of the group communication button by a user on a user interface, and initiating a group communication session with a device of a contact associated with the quick contact group communication shortcut icon.

RELATED APPLICATIONS

This application is a divisional application of U.S. patent applicationSer. No. 13/661,371, filed Oct. 26, 2012, which claims the benefit ofpriority to U.S. Provisional Patent Application No. 61/554,876, filedNov. 2, 2011, the entire contents of both of which are herebyincorporated by reference for all purposes.

This application is also related to U.S. patent application Ser. No.13/661,378 entitled “User Experience Enhancements for Limiting Calls ina Group Communication” filed Oct. 26, 2012.

BACKGROUND

The present invention generally relates to wireless telecommunicationsystems. More particularly, the present invention relates to methods anddevices which enable group communication, such as “Push-To-Talk” (PTT)communication, without requiring dedicated PTT hardware.

In wireless telecommunication devices, such as cellular phones, PDAs,mini-laptops, and advanced pagers, the devices typically communicateover long distances by bridging telephone calls through existingcellular telephone networks and passing data packets across the network.These wireless communication devices often have data processing andcomputing capabilities, and can accordingly send and receive voice andother types of data across the telephone network.

There exists a wireless telecommunication service that provides a quickone-to-one or one-to-many communication that is generically referred toas “Push-To-Talk” (PTT) capability. The specific PTT group of recipientdevices for the communicating wireless communication device is commonlyset up by the carrier. A PTT communication connection is typicallyinitiated by a single hardware button-push on the wireless communicationdevice that activates a half-duplex link between the speaker and eachmember device of the group and once the button is released, the devicecan receive incoming PTT transmissions. Existing PTT systems haveadvantages over traditional cellular systems because they have fastercall setup times, e.g., setup times ideally in the range of 1 second asopposed to cellular voice channels that can take more than 5 seconds toestablish. In some arrangements, the PTT speaker will have the “floor”where no other group member can speak while the speaker is speaking.Once the speaker releases the PTT button, any other individual member ofthe group can engage his or her PTT button and he or she will have thefloor. Generally speaking, the PTT system uses standard voice-overInternet protocol (VoIP) technologies. Voice information is sent indigital form over IP-based data networks. In PTT scenarios, instead ofusing the standard cellular infrastructure a call is formed by combiningseparate point-to-point connections between each IP endpoint in thenetwork. Initiating the PTT system generates a call to the targetdevice. The call originator's voice can be sent through the carrier'snetwork to the target handset.

A drawback to existing PTT services is that they typically requiredevices with dedicated PTT hardware components, such as a hardware PTTbutton, meaning that these services are generally not available for themajority of mobile devices in use today.

SUMMARY

The various embodiments include methods for managing a groupcommunication session on a wireless communication device, includingdisplaying a quick contact group communication shortcut icon on a homescreen of a wireless communication device display, displaying a groupcommunication button in association with the the quick contact groupcommunication shortcut icon on the home screen of the display, detectinga selection of the group communication button by a user on a userinterface, and initiating a group communication with a device of acontact associated with the quick contact group communication shortcuticon. Further embodiments may include displaying a locking mechanism inassociation with the quick contact group communication shortcut icon.

Various embodiments include wireless communication devices includingprocessors configured to perform operations of the embodiment methodsdisclosed herein. Various embodiments also include wirelesscommunication devices including means for performing functions of theembodiment methods disclosed herein. Various embodiments also includenon-transitory processor-readable storage media having stored thereonprocessor-executable instructions configured to cause a processor toperform operations of the embodiment methods disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutepart of this specification, illustrate exemplary embodiments of theinvention, and together with the general description given above and thedetailed description given below, serve to explain the features of theinvention.

FIG. 1 illustrates a wireless communication device suitable for use withvarious embodiments.

FIG. 2 is a diagram illustrating software layers of a group applicationclient that may include “Push To Talk” (PTT) functionality.

FIG. 3 depicts an example system for group communication between aplurality of wireless communication devices.

FIG. 4 shows an example wireless network suitable for use with variousembodiments.

FIG. 5 is a process flow diagram of an embodiment method of groupcommunication in which visual feedback regarding the state of the groupcommunication session is displayed on a display screen of a wirelesscommunication device.

FIGS. 6A-6C are screenshots of a touchscreen user interface of anembodiment wireless communication device.

FIG. 7 is a process flow diagram of an embodiment method of groupcommunication that includes displaying visual feedback to indicatecontrol of the floor in a PTT communication session.

FIGS. 8A-C are screenshots of a touchscreen display illustrating anembodiment PTT communication session.

FIG. 9A is a process flow diagram of an embodiment method of groupcommunication that includes displaying visual feedback to indicate thestatus of the floor in a group communication session.

FIG. 9B is a process flow diagram of an embodiment method of groupcommunication using a server that may transmit a state of floor control.

FIG. 1 OA is a process flow diagram of an embodiment method of groupcommunication that includes displaying visual feedback of theparticipation state of one or more devices in a communication group.

FIG. 10B is a process flow diagram of an embodiment method of groupcommunication that includes displaying visual feedback of theparticipation state of one or more devices and the reason(s) fornon-participation of at least one non-participating device in acommunication group.

FIG. 10C is a process flow diagram of an embodiment method of groupcommunication using a server that may indicate to devices in the groupthe participation state and/or reason(s) for non-participation of atleast one device in the group.

FIGS. 11A-11D are screenshots of an embodiment touchscreen displayhaving a sliding lock mechanism.

FIG. 12 is a process flow diagram of an embodiment method of groupcommunication using a “hands-free” mode.

FIG. 13A is a process flow diagram of an embodiment method of groupcommunication using a “priority lock” mode.

FIG. 13B is a process flow diagram of an embodiment method of operationof a server in a group communication session in which a user devicerequests priority floor access.

FIG. 14A is a process flow diagram of an embodiment method of groupcommunication using a “media lock” mode.

FIG. 14B is a process flow diagram of an embodiment method of operationof a server in a group communication session in which a user devicerequests a media lock.

FIG. 15A is a process flow diagram of an embodiment method of groupcommunication using a “lockout” mode.

FIG. 15B is a process flow diagram of an embodiment method of operationof a server in a group communication session in which a user deviceactuates a lockout mechanism.

FIG. 16A is a process flow diagram of an embodiment method of groupcommunication using a “blocking” mode.

FIG. 16B is a process flow diagram of an embodiment method of operationof a server in a group communication session in which a user deviceactuates a blocking mechanism.

FIGS. 17A-C are screenshots of an embodiment touchscreen display havinga “quick contact” group communication shortcut on a home screen.

FIG. 18A is a process flow diagram of an embodiment method of groupcommunication using a “quick contact” group communication shortcut.

FIG. 18B is a process flow diagram illustrating an embodiment method ofgroup communication using a “quick contact” shortcut and a slidinglocking mechanism.

FIG. 19 is a system block diagram of a wireless communication device foruse with various embodiments.

FIG. 20 is a system block diagram of a server suitable for use withvarious embodiments.

DETAILED DESCRIPTION

The various embodiments will be described in detail with reference tothe accompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.References made to particular examples and implementations are forillustrative purposes, and are not intended to limit the scope of theinvention or the claims.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any implementation described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other implementations.

The terms “mobile device,” “mobile computing device” and “wirelesscommunication device” are used interchangeably herein to refer to anyone or all of cellular telephones, smartphones, personal or mobilemulti-media players, personal data assistants (PDA's), laptop computers,tablet computers, smartbooks, palm-top computers, wireless electronicmail receivers, multimedia Internet enabled cellular telephones,wireless gaming controllers, and similar personal electronic deviceswhich include a programmable processor and memory and may includesoftware and/or hardware to enable group communication, such aspush-to-talk (PTT), functionality.

In overview, various embodiments provide enhanced group communication,such as “Push-To-Talk” (PTT), functionality in a wireless communicationdevice using software and native device hardware, such as a touchscreendisplay. The various embodiments may be implemented on a wide range ofdevices, including most Internet-enabled mobile phones and otherwireless communication devices, and do not require dedicated hardware,such as a PTT button, to provide group communication functionality.

Previously, push-to-talk services required dedicated hardware, such as aPTT button, for the user to take advantage of the service. The variousembodiments provide a user-experience that combines many of theadvantages of a conventional hardware-based PTT service with a number ofenhanced features that are made possible through the use of a groupcommunication service that is primarily implemented through software.

Various embodiments are directed to a novel group communicationinterface that can provide enhanced functionality as compared toconventional hardware-implemented PTT services. Because the presentembodiments are primarily implemented in software, the user no longerneeds to “push” a physical button to talk. In various embodiments, theuser interface can allow the user to “lock” control of the floor in ahands-free mode, which allows the user to more easily multitask and toutilize the device speakerphone and/or earpiece mode in a more naturalway. Additional functionality can also be added, such as the ability tolock control of the floor for media content, as well as the ability toat least temporarily modify the criteria for floor control andmediation, which may be useful when the user desires priority access ofthe floor for a limited time. The additional functionality may alsoinclude the ability to lock out another device in a communication groupfrom receiving outgoing communications from the user's device, as wellas the ability to block the user's device from receiving groupcommunications from another user. Some or all of this addedfunctionality may be provided via a target-based sliding lock, which maybe implemented in a touchscreen user interface display.

Various embodiments additionally enable the user to create a “quickcontact” shortcut on their home screen or as a device widget. Selectingthis shortcut brings up a modified PTT “button” on the screen, which mayalso include the “hands-free”lock, so that the user effectively has the“one-click” PTT experience that is advantageous in conventionalhardware-implemented PTT, but on the wider range of devices that mayprovide a software-implemented group communication service. The quickcontact shortcut avoids the issue of the user having to find, launch andnavigate through a group communication application program in order tospeak to their contact.

Various embodiments may implement a more visual experience than ispreviously employed, and may utilize visual feedback cues to the userwhich may augment or replace the existing audio cues for floor controland mediation. The visual feedback cues may be provided via graphicalelements and colors on the display screen of the wireless device. Invarious embodiments, the feedback cues may show the state of a groupcommunication session, and may indicate, for example, control of thefloor for group communication. In various embodiments, the displayscreen may display visual features which tell the user when the floor isopen, when the floor is requested by user's device, when the floorcontrolled by user's device or by a different device. In someembodiments, the display screen may also display visual representationsof the members of the group in the group communication, and may furtherdisplay the participation state(s) of each member of the group. Forexample, the device may display the members of the group who arecurrently participating in the group communication session as well asthe members of the group who are not participating in the groupcommunication session. In various embodiments, the device mayadditionally display reasons why the non-participating members are notparticipating in the communication. These enhanced features may beimplemented in software which runs on the user's wireless device, andmay also be implemented in part in a server.

Referring now to FIG. 1, it illustrates an example wirelesstelecommunication device that can be a wireless communication device 100that includes software and/or hardware to provide a group communication(e.g. “Push-To-Talk” (PTT)) function that opens the direct communicationto a target device, e.g., an endpoint associated with an IP address. Invarious embodiments, the wireless communication device 100 providesgroup communication functionality using only software and existingdevice hardware (e.g., a conventional user interface/display, such as akeypad or touchscreen interface). The embodiment device 100 of FIG. 1 isshown having a touchscreen interface/display 104. In variousembodiments, no dedicated PTT hardware, such as a PTT button ordedicated PTT circuitry is required to provide the PTT functionality.

In various embodiments, the wireless communication device 100 mayinclude a computer platform 106 that can handle voice and data packets,execute software applications, and transmit information across awireless network. The computer platform 106 includes, among othercomponents, a processor 108 such as an application-specific integratedcircuit (“ASIC”) or a RISC processor such as those that implement theARM architecture. The processor 108 is typically installed at the timeof manufacture of the wireless communication device 100 and is notnormally upgradeable. The processor 108 or other processor executes anapplication programming interface (“API”) layer 110, which includes theresident application environment, and may include the operating systemloaded on the processor 108. The resident application environmentinterfaces with any resident programs in the memory 112, e.g., acomputer readable storage medium of the wireless communication device100.

As shown here, the wireless communication device 100 may be a wirelesscommunication telephone, with a graphics display 104, but may also beany wireless device with a computer platform 106 as known in the art,such as a personal digital assistant (PDA), a pager with a graphicsdisplay 104, or even a separate computer platform 106 that has awireless communication portal, and may otherwise have a wired connectionto a network or the Internet. Further, the memory 112 may be comprisedof read-only or random-access memory (RAM and ROM), EPROM, EEPROM, flashcards, or any memory common to computer platforms. The computer platform106 may also include a local database 114 for storage of softwareapplications not actively used in memory 112. The local database 114 istypically comprised of one or more flash memory cells, but may be anysecondary or tertiary storage device as known in the art, such asmagnetic media, EPROM, EEPROM, optical media, tape, or soft or harddisk. The graphics display 104 may present not only information aboutthe ongoing group call, but also the information about the data packagein order to generate a preview as is more fully described herein.

The computer platform 106 may also include a direct communicationinterface 116 that is configured to open a direct communication channel.The direct communication interface 116 may also be part of the standardcommunication interface for the wireless communication device 100 whichordinarily carries the voice and data transmitted to and from thewireless communication device 100. The direct communication interface116 typically is comprised of hardware as is known in the art.

FIG. 2 is a diagram of an embodiment of software layers of a groupapplication client that can include, but is not limited to, PTTfunctionality and data package functionality. While the embodiment shownherein is implemented in a PTT session, the present system can beutilized in any group communication session setup for transmission ofvoice and/or data substantially simultaneously among group members. Inan embodiment, the computer platform 106 in the wireless communicationdevice environment may include a series of software “layers” developedon top of a baseband chipset and system software such as the Wirelesscommunication Station Modem (MSM) 218 and the Advanced Wirelesscommunication Subscriber Software (AMSS) 220, developed by QUALCOMM®. Inthis example, the underlying MSM chipset may implement the softwareprotocol stack for the entire suite of CDMA communication technologiesthat include CDMA2000 1X and CDMA2000 1xEV-DO. In this example the AMSS220 may be configured to support a wireless communication operatingsystem layer 222, which in an embodiment is BREW® also developed byQUALCOMM®. The wireless communication operating system layer 222 mayprovide an application programming interface for chip or device-specificoperations, while providing an isolation layer that eliminates directcontact to the AMSS 220 and any OEM software on the computer platform.The wireless communication operating system layer 222 may enableapplication development that uses wireless communication device featureswithout having to rewrite the application each time a new release of thedevice-specific software is released.

In this example the wireless communication operating system 222 mayinclude a PTT client 226 that is configured to offer access to PTTservices through an external interface, here shown at a PTT-aware UI224. The PTT client 226 may include all the functions required to enablewireless communication operating system 222 applications, such as themedia client 228. In an embodiment, the PTT client 226 may maintainaccess to PTT services, respond to communication requests, process allPTT-aware wireless communication operating system applications requestsfor PTT services, process all outgoing PTT requests, collect and packagevocoder packets for originating PTT talk spurts, and parses packets ofvocoder data for terminated PTT talk spurts.

In various embodiments, the computer platform 106 in the wirelesscommunication device environment may include a media client 228, whichmay be a wireless communication operating system-based application thatextends PTT services for access to media types other than thetraditional half duplex voice communications (VoIP-PTT media). The mediaclient 228 may provide access to media services through an externalinterface such as a media aware API that is an application that may bedeveloped entirely as a wireless communication operating system-basedapplication or used in combination with an AMSS 220 interface. The mediaclient 228 may service requests from the user and inform the user of theresult of any group-directed media request. The media client 228 mayadditionally be configured to handle incoming notifications thatindicate there is data package to download from a media server 316 ofFIG. 3 and described in more detail below. For example, the media client228 may be configured in one embodiment to download data packagesimmediately or in other embodiments the media client 228 may beconfigured to download the data package at a predetermined time period,e.g., at 10:00 pm daily, or it may be configured to prompt the user viathe PTT UI 224 to determine whether and/or when to download the file.Other applications 230, which may be push-to-talk or other applicationsthan can receive and transmit data across the group communicationchannel, may also be resident on the platform.

In some embodiments, the software to enable PTT functionality in thewireless communication device 100 may be pre-installed in the deviceduring device manufacture. In other embodiments, at least a portion ofthe software providing PTT functionality may be downloaded to the device100 by the end-user. In some embodiments, the PTT software may be adownloadable application (e.g., a mobile app).

FIG. 3 illustrates an example embodiment of a system 300 for sharingdata packages among one or more wireless telecommunication devices in aPTT group 302, such as the wireless communication device 100, smartphone301, tablet computer 303, smart pager 304 and personal digital assistant(PDA) 306, with other wireless communication devices. In the system 300,each wireless telecommunication device 100, 301, 303, 304, and 306 maybe capable of selectively directly communicating across the wirelesscommunication network 308 with a target set of one or more otherwireless telecommunication devices. For example, the target set forwireless communication device 100 may be all devices in thecommunication group 302 or a subset thereof, such as smartphone 301,tablet computer 303, pager 304 and PDA 306.

In an embodiment, the wireless telecommunication device 100 may send aflag to at least the communications server 310, which is present on aserver-side LAN 312 across the wireless network 308. The flag in thisexample may be used by the server to determine that the wireless deviceis present, i.e. is accessible, on the wireless network 308. Thecommunication server 310 may share this information with a set of targetwireless telecommunication devices designated by the first wirelesstelecommunication device or it may also share this with other computerdevices resident on the server-side LAN 312 or accessible across thewireless network 308. The communication server 310 may have an attachedor accessible database 314 to store the group identification data forthe wireless devices. In various embodiments, a media server 316, whichmay additionally include circuitry for a file management server, may bepresent on the server-side LAN 312. It should be appreciated that thenumber of computer components resident on server-side LAN 312, or acrossthe wireless network 308, or Internet generally, are not limited.Furthermore, some or all of the functions of the several server-sidecomponents described herein, such as communications server 310, database314 and media server 316, may be combined in a single device.

In various embodiments, the communications server 310, which may also bereferred to as a group communications server, may establish point topoint IP PTT channels between devices in the group 302. A PTT channelmay be established through a half-duplex channel (true or virtual)between the communicating wireless communication device 100, 304, and/or306 and the one or more other wireless communication devices of thetarget set. Also, in various embodiments the communication server 310may attempt to bridge the requested direct communication with the targetset if at least one of the wireless communication devices of the targetset have informed the communication server 310 of their presence on thewireless network 308.

The communications server 310 may also inform the wireless communicationdevice 100, 304, and 306 of the inability to bridge a directcommunication to the target set 302 upon none of the wirelesstelecommunication devices (or at least one) of the target set not havinginformed the group communication server 310 of their presence on thewireless network 308. Further, while the communications server 310 isshown here as having the attached database 314 of group identificationdata, the group communication server 310 device may have group identitydata resident thereupon, and perform all storage functions describedherein.

In various embodiments, the communication server 310 may performarbitration functions between competing demands of the various wirelesscommunication devices 100, 304, 306 for use of PTT communicationchannels over wireless network 308. For example, in response to arequest from wireless communication device 100 to communicate with oneor more other target devices in PTT group 302, including all otherdevices in the group 302, the communication server 310 may establish aPTT channel between the requesting device 100 and all or a portion ofthe requested target devices in group 302. The communication server 310may thus grant control of the “floor” to the requesting wirelesscommunication device 100. When competing requests exist amongst devicesof the group 302 for control of the “floor,” the communication server310 may arbitrate between competing requests based on pre-determinedpriority criteria. The priority criteria may be established at the timeof the PTT group 302 formation, such as by a group administrator, andstored in communication server 310 and/or database 314. In variousembodiments, the priority criteria may be default priority criteriastored in server 301 and/or database 314. In some embodiments, thepriority criteria may be established on an ad hoc basis by one or moreof the wireless communication devices 100, 304, 306 in the PTT group302.

In overview, the system 300 may include at least one wirelesscommunication device, such as wireless communication device 100, thatmay be a member of a PTT communication group 302 of wirelesscommunication devices. The wireless communication devices in thisexample may be configured to communicate with each other or communicateas a group across a wireless communication network 308. In addition, invarious embodiments at least one of the wireless communication devicesmay be configured to selectively send data packages to other members ofthe communication group 302. At least one communications server 310 maybe configured to store information on communication groups 302 on thewireless communication network 308, the information including theidentity of the specific member wireless communication devices of one ormore communication groups. The communications server 310 may be furtherconfigured to selectively receive data packages from a sending wirelesscommunication device, such as wireless communication device 100, of acommunication group 302.

In various embodiments, the media server 316 may be configured toreceive the data packages from the wireless communication device (suchas wireless communication device 100) and selectively permit members ofthe communication group 302 to access the stored data packages acrossthe wireless communication network 308. In an embodiment data packagesmay include, but are not limited to, pictures in JPEG, TIF, and thelike, audio files such as MP3, MP4, WAV, and the like, documents, and/orpresentations. The data packages may additionally include streamingmedia, such as a multimedia application (PowerPoint, MOV file, and thelike). Also, the data packages may include half-duplex videoconferencing among members of the communication group wherein thepicture of the speaker may be broadcast to the other group members insubstantial real-time, or in delay.

The size of the data package files can be very large and because of thepotential delay of sending the media, or inability of the receivingwireless communication device to handle the sent media, the system 300may use a media server 316 to store the data packages such that targetmembers of the communication group 302 can selectively access the storedmedia without interrupting other PTT communications. Alternatively, inone embodiment, if the data packages are stored at the media server 316,the media server 316 may be configured to send a hypertext link to theoriginating device or the target wireless communication devices of thecommunication group 302. The hypertext link in this example may providea link to the stored group-directed media at the media server 316. Uponreceipt of data packages by at least one of the member wireless devicesof the communication group 302, the communications server 310 may sendan acknowledgement indicating to the wireless communication device 100,304, and 306 that at least one member wireless communication device ofthe communication group 302 received the data package.

The wireless communication device 100, 304, 306 may send communicationgroup identification data to the communications server 310 at the timeof sending a data package, e.g. a target list, and thus, the mediaserver 316 may be configured to send or store the data package to or forthe member wireless communication devices identified in thecommunication group identification data based upon a variety ofcriteria. Alternately, prior to the wireless communication devicesending data packages, the wireless communication device 100, 304, and306 may request member data for a communication group 302 from thecommunications server 310, and the server 310 may send one or moreaddresses or communication group addresses to the wireless communicationdevice 100, 304, and 306. In an embodiment, the communications server310 may filter the potential communication groups available based upontheir member devices' capability to receive data packages.

As is further described herein, the wireless communication device 100,304, and 306 may be engaged in a group communication with the memberwireless communication devices of the communication group 302, and senddata packages during the group communication in the same communicationsession, either to all members or a subset thereof. Alternately, thedata packages may be sent independently of the group-communicationsession.

FIG. 4 shows an exemplary wireless network in a common cellulartelecommunication configuration. The wireless network in this exampleincludes a series of communications servers 310 that controlcommunications between the wireless communication devices of set groupmembers (devices 100-A through D) in a PTT system. The wireless networkis merely exemplary and can include any system whereby remote modulescommunicate over-the-air between and among each other and/or between andamong components of a wireless network, including, without limitation,wireless network carriers and/or servers. A series of communicationsservers 310 may be connected to a group communication server LAN 312.Wireless devices 100-A through D may request voice (e.g., VoIP) and/orpacket data sessions from the group communications server(s) 310.

Continuing with the description of FIG. 4, the communications server(s)310 in this example may be connected to a wireless service provider'spacket data service node (PDSN) such as PDSN 414, shown here resident ona carrier network 416. When a wireless communication device accesses thewireless data network to obtain services, the PDSN 414 may interfacewith an authentication, authorization, and accounting server “AAA” 428to authenticate the wireless communication devices 100, 304, and/or 306.The AAA 428 may be coupled to a database operable to store informationsuch as user accounts and privileges. Each PDSN 414 may interface with abase station controller 418 of a base station 320 through a packetcontrol function (PCF) 422. The PCF 422 may be located in the basestation 420. The wireless network 308 may control messages (generally inthe form of data packets) sent to a messaging service controller (“MSC”)424. The carrier network 308 in this example may communicate with theMSC 424 by a network, the Internet and/or POTS (“plain ordinarytelephone system”). Typically, the network or Internet connectionbetween the wireless network 308 and the MSC 424 transfers data, and thePOTS transfers voice information. The MSC 424 may be connected to one ormore base stations 420. In a similar manner to the carrier network, theMSC 424 is typically connected to the branch-to-source (BTS) 426 by boththe network and/or Internet for data transfer and POTS for voiceinformation. The BTS 426 ultimately broadcasts and receives messageswirelessly to and from the wireless devices, such as devices 100-Athrough D, which may be cellular telephones, by short messaging service(“SMS”), or other over-the-air methods known in the art. It should alsobe noted that carrier boundaries and/or PTT operator network boundariesdo not inhibit or prohibit the sharing of data as described herein.

Wireless communication telecommunication devices, such as mobile orwireless telephones, are being manufactured with increased computingcapabilities and are becoming tantamount to personal computers andhand-held PDAs. These “smart” cellular telephones allow softwaredevelopers to create software applications that are downloadable andexecutable on the processor of the wireless device. The wireless device,such as device 100, can download many types of “data packages,” whichare discrete segments of computer code, such as applications, web pages,applets, MIDlets, multi-media, picture, games and simple data. Inwireless devices that have designated a communication group 302 (such asdepicted by FIG. 3), the wireless communication device may directlyconnect with the other member of the set and engage in voice and datacommunication. However, in various embodiments, such direct groupcommunications may occur through, or at the control of, the groupcommunication server 310. All data packets of the devices do notnecessarily have to travel through the communication server 310 itself,but in various embodiments the communication server 310 is preferablyable to ultimately control the communication because it is typically theonly server-side component that is aware of and/or can retrieve theidentity of the members of the communication group, or direct theidentity of the members of the communication group 302 to anothercomputer device.

FIG. 5 is a process flow diagram illustrating an embodiment method 500of communicating over a wireless network using a wireless communicationdevice with group communication functionality, such as “Push-To-Talk”(PTT) functionality. The various embodiment methods may be describedherein as utilizing a “Push-To-Talk” function, though it will beunderstood that the embodiment methods may be applicable to other typesof group communication. FIGS. 6A-6C are screenshots of a touchscreenuser interface 104 of an exemplary wireless communication device 100suitable for practicing the method 500 according to one embodiment. Invarious embodiments, the wireless communication device 100 providesgroup communication, such as PTT communication, using software andnative device hardware, such as a touchscreen display 104 and/or otheruser interfaces, such as a keypad interface. In various embodiments, thePTT methods described herein may be implemented on a wide range ofdevices, including most Internet-enabled mobile phones and otherwireless communication devices. In various embodiments, the methods maybe implemented using wireless communication devices that do not includededicated PTT hardware, such as a PTT button or PTT-specific circuitry.

As shown in method 500, the wireless communication device 100 maydownload group communication application software, such as PTTapplication software, in optional block 502. The group communicationapplication software may include all or a portion of group communicationclient software, such as described above in connection with FIGS. 1 and2. In various embodiments, a downloadable version of the groupcommunication application software allows devices which are capable ofsupporting group communication to download and run the groupcommunication application to provide the wireless device with groupcommunication functionality. In other embodiments, the wireless device100 may have factory-installed group communication application software,in which case the optional block 502 may not be performed.

The wireless communication device 100 may establish a group of one ormore other wireless communication devices for group communication (e.g.,a “group communication group”) in optional bock 504. It will beunderstood that a group communication group may include one otherdevice. A group communication group may also comprise a plurality ofother devices to enable “multi-cast” or “broadcast” communication withthe plurality of devices over a wireless network using the groupcommunication function. As shown in FIGS. 6A-C, for example, a groupcommunication group (“College Friends”) has been established whichincludes six devices, the user's own wireless device 100 and five otherdevices.

In various embodiments, the group communication group may be establishedby the user or users of the various wireless devices, for example, in anad hoc process. The establishment of a group communication group may beperformed through or under the control of a server, such ascommunication group server 310 as described above in connection withFIGS. 3 and 4. It will be understood that a plurality of different groupcommunication groups may be established, and a single wirelesscommunication device 100 may be included in a plurality of differentgroup communication groups, and may communicate with devices of any oneof the groups using the group communication function. In someembodiments, one or more group communication groups may be previouslyestablished on the wireless communication device 100, such as by asystem administrator, in which case the optional block 504 may not beperformed.

In block 506, the wireless communication device 100 may initiate thegroup communication function in response to input from the user of thedevice 100. For example, the user may select from a menu and launch agroup communication application on the wireless device 100 using asuitable user interface, such as the touchscreen display 104 of FIGS.6A-C. The initiation of the group communication function may alsoinclude the selection of a group communication group with which toestablish a group communication session, wherein the group communicationgroup may consist of one or more wireless communication devices.

In block 508, the wireless communication device 100 may display thestate of the group communication session using visual feedback on thedisplay screen 104 of the device 100. As described in further detailbelow, the display screen 104, which in various embodiments consists ofa touchscreen, may display visual feedback cues, including graphicalelements and/or colors, to indicate the various states of the groupcommunication session, such as floor status (i.e., floor open, floorgranted, etc.), the status of other group member(s), the existence oflong connection times, etc.

Referring to the exemplary embodiments of a touchscreen display 104shown in FIGS. 6A-6B, in FIG. 6A is shown a touchscreen display 104 inwhich a group communication application, specifically a PTT application,has been initiated. The display 104 identifies a group 602 with which aPTT communication session has been established, and further displays aplurality of icons 604 representing the individual members of the group602. A virtual PTT button 606 is displayed on the screen 104. In variousembodiments, a virtual PTT button 606 may function much like aconventional hardware PTT button. When the device 100 detects a touchevent on the virtual button 606, the device 100 may transmit a requestto the communication server 310 to open a communication channel from thewireless device 100 to the other device(s) in the PTT group. FIG. 6Billustrates an exemplary embodiment of a display 104 which shows aneutral state of the PTT session, in which the PTT session has beeninitiated, such as by the user's finger 610 touching the virtual PTTbutton 606, but no communication channel is currently established (i.e.,the “floor” is open). FIG. 6C illustrates the display 104 where theuser's finger 610 is touching the virtual button and a communicationchannel from the wireless device 100 to other devices in the group isestablished and open (i.e., the “floor” has been granted to the wirelesscommunication device 100). In this state, the wireless communicationdevice 100 may transmit voice and/or other data across wireless networkto the other device(s) in the PTT group. As shown in FIG. 6C, this state(i.e., floor granted to device 100) may be indicated by a change incolor over a portion 608 of the display 104.

FIG. 7 is a process flow diagram illustrating an embodiment method 700of group communication, such as PTT communication, using visual feedbackof the state of the group communication session. In block 702, thewireless communication device 100 may begin a group communicationsession as described above. In block 704, the device 100 may display thestate of the group communication session using visual feedback on adisplay screen 104, which may be a touchscreen display. In block 706,the device 100 may detect the initiation of a group communication by theuser on the user interface of the device 100. In various embodiments,this may include the detection of a touch event at a “virtual” PTTbutton, such as described above in connection with FIG. 6A. In otherembodiments, such as in devices without a touchscreen interface, thismay include the detection of a key entry on a keypad interface. In block708, the device 100 may send a request to a server, such ascommunication server 310 described above, for the “floor” for a groupcommunication. In block 710, the device 100 may display visualfeature(s) indicating a group communication state of floor requested butnot granted. In various embodiments, the visual features for this statemay correspond to the “neutral” state shown in FIG. 6B. In otherembodiments, this state could be indicated by color coding, such as ared or yellow screen when the floor has been requested but not granted,which can change to a different color, such as green, when the device100 is granted the floor. While the floor is requested but not yetgranted (i.e., determination block 712=No), the device 100 may continueto display visual features indicative of this state. When the floor isgranted (i.e., determination block 712=Yes), the device 100 may displayvisual features indicating that the floor is granted to the user'sdevice 100. As discussed above, these visual features may include achange in color of all or a portion of the display screen 104 (such asfrom red or yellow to green), or it may include the display of othergraphical feedback cues. It will be understood that in addition to thevisual feedback cues described herein, other feedback cues, such asaudio or haptic cues, can also be employed to indicate the state of thegroup communication.

FIGS. 8A-C are further screenshots of a touchscreen display 104illustrating an embodiment group communication session, specifically aPTT communication session. FIG. 8A shows the screen displaying visualfeatures indicating that the floor is granted to the user's device 100,as discussed above in connection with FIG. 6C. In this embodiment, thedevice 100 displays a color change over a portion 608 of the screen whenthe floor is granted. The user's thumb 610 is shown touching the screen.FIG. 8B shows the screen displaying visual features indicating a neutralstate in which the floor is open. In this embodiment, the display 104may indicate that the floor is open, and that a touch event on thedisplay 104 or on a portion 804 thereof (e.g., “Push to Talk”) willcause the device 100 to request control of the floor for a groupcommunication. FIG. 8C shows the screen displaying visual featuresindicating that another user's device has control of the floor. Thisstate may be indicated by a change in graphics and/or color on thedisplay screen 104. In this embodiment, this state is indicateddisplaying the contact icon 802 (e.g., photograph) of the user whosedevice currently controls the floor (e.g., the person speaking) in thegroup communication session.

FIG. 9A is a process flow diagram illustrating an embodiment method 900of group communication using visual feedback of the state of the groupcommunication session. In block 902, the user's wireless communicationdevice 100 may receive a communication from a server, such as groupcommunication server 310 described above, indicating a status of floorcontrol in a group communication session. When the floor is granted tothe user's device (i.e., determination block 904=Yes), then the device100 may display, on a display screen, visual features indicating a groupcommunication state of floor granted to the user's device 100 in block906. The visual features may include graphical elements and/or changesin color, as described above. An example of a device screen in a groupcommunication state of floor granted to the user's device according toone embodiment is shown in FIG. 8A. When the floor the floor iscontrolled another device in the group communication group (i.e.,determination block 908=Yes), then the device 100 may display, on thedisplay screen 104, visual features indicating a group communicationstate that the floor is granted to a different user's device in block910. The visual features may include graphical elements and/or changesin color, as described above. An example of a device screen in thisstate is according to one embodiment is shown in FIG. 8C. In thisembodiment, the visual feature may include a contact icon of the userwhose device controls the floor in the group communication, as shown inFIG. 8C. When the floor is not controlled by the user's device (i.e.,determination block 906=No), and the floor is not controlled by anyother device in the group communication group (i.e., determination block908=No), then the device 100 may display, on the display screen 104,visual features indicating a neutral state in which the floor is open inblock 912. The visual features may include graphical elements and/orchanges in color, as described above. An example of a device screen in aneutral state according to one embodiment is shown in FIG. 8B.

The device 100 may maintain the various visual feedback featurescorresponding to the group communication state in blocks 906, 910 and912, respectively, until the device 100 receives a floor statuscommunication from server in block 902, and the above process mayrepeat.

FIG. 9B is a process flow diagram illustrating an embodiment method 901of group communication using a server, such as group communicationserver 310 shown in FIGS. 3 and 4. The server 310 may receive requestsfrom user devices in a group communication group for control of thefloor in a group communication session in block 914. The server 310 maydetermine control of the floor based on pre-determined criteria, asdiscussed above, in block 916. The server 310 may transmit messages tothe devices in the group indicating which device has control of thefloor in block 918. The server 310 may also transmit media contentand/or other data to the devices in optional block 920. This transmitteddata may be usable by the devices in displaying visual feedback of thestate of floor control in the group communication session. For example,the server 310 may send image file(s) or other information which may bedisplayed by the devices in the group while a particular device hascontrol of the floor. In various embodiments, the devices may determinewhether or not to use the transmitted data in displaying a visualindication of the state of floor control.

Referring again to FIGS. 8A-C, in various embodiments, a wirelesscommunication device 100 can include a display 104 that displays visualfeedback of the participation state of one or more devices in a groupcommunication, such as a PTT communication. In various embodiments, thedevice 100 may display visual feedback that indicates which users from agroup are available to participate in a group communication as well aswhich users from the group are not available. In various embodiments,the device 100 may also display the reason(s) why one or more users arenot available to participate in a group communication. As shown in FIG.8A, the display screen 104 of the device 100 may display anidentification of a group 806 with which a group communication sessionhas been initiated, which may include the name of the group (e.g.,“College Friends”), the number of members of the group, as well as thegroup members currently participating in the group communication session(e.g., “You+3/5”). The display screen 104 may also display icons 810,812, 814 representing each of the members of the group. The displayscreen 104 may display only a limited number of icons, and may enablethe user to scroll through to view additional icons and/or may include aseparate icon 816 to enable the user to view the icons of additionalgroup members. The icons may include photographs 810 of the groupmembers when available, and may include a default icon 812 where aphotograph is not available. Icon 814 represents a member of the groupwho is not participating in the group communication session. In variousembodiments, icon 814 of a non-participating group member may includedifferent visual characteristics than the icons 810, 812 ofparticipating group members. In the embodiment illustrated in FIG. 8A,for example, icon 814 has a darker color than the other icons 810, 812,and is also partially faded out. Any suitable graphical features can beutilized to indicate the participation state(s) of the various members.In various embodiments, the display 104 can include visual features toindicate the reason for non-participation of one or more group members.In some embodiments, the user may click on the icon 814 of anon-participating member to display the reason for non-participation,such as the member is busy (e.g., on another call), unreachable (e.g.,the member's device is out of the coverage area or not enabled for groupcommunication), unavailable (e.g., the user's device is turned off), oris otherwise not participating in the call (e.g., the member has placedhis/her device on “mute”). In various embodiments, the user may be ableto set the status of his or her wireless device (e.g., “I am in ameeting until 2 pm and unavailable to talk”), and this reason fornon-participation may be displayed on the devices of other members ofthe group.

FIG. 10A is a process flow diagram illustrating an embodiment method1000 of group communication that includes visual feedback of theparticipation state of one or more devices in a communication group. Inblock 1002, a wireless communication device 100 may receive a request toinitiate and/or join a group communication session with a groupconsisting of one or more member devices. The request may be receivedfrom the user of the device 100 on a user interface, such as atouchscreen display or a keypad interface. The request may also bereceived from another device within the communication group, or from aserver, such as group communication server 310. In block 1004, thedevice 100 may display, on a display screen, a visual representation ofthe one or more members of the communication group. The visualrepresentation of the one or more members may include icons representingeach of the members of the group, as shown in FIG. 8A. In variousembodiments, the various members of the communication group may beaccessed from memory on device 100. In some embodiments, the members ofthe communication group may be determined via communication with aserver, such as group communication server 310, or via communicationwith one or more other devices on the wireless network. In block 1006,the device 100 may determine a participation state of each member of thegroup. The determining a participation state may include determiningwhether each member device is participating or is not participating inthe group communication session. In various embodiments, theparticipation states of the various members may be determined viacommunication with a server, such as group communication server 310, orvia one or more other devices on the wireless network. In block 1008,the device 100 may display visual features indicating the participationstate of each of the one or more members of the group. In variousembodiments, an icon representing a non-participating group member mayinclude different visual characteristics than the icons of participatinggroup members, such as shown in FIG. 8A. When the participation state ofa group member changes (i.e., determination block 1010=Yes), the device100 may determine the updated participation states in block 1006 anddisplay visual features indicating the updated participation states inblock 1008. This may process may continue while the session is active(i.e., determination block 1012=No). The session may be terminated(i.e., determination block 1012=Yes) in block 1014.

FIG. 10B is a process flow diagram illustrating an embodiment method1001 of group communication that includes visual feedback of theparticipation state of one or more group member devices in acommunication group and additionally display of the reason(s) fornon-participation in the communication session by one or morenon-participating group member devices. Bocks 1016-1020 are similar toblocks 1002-1006 of method 1000 shown in FIG. 1 OA, and includereceiving a request to initiate and/or join a group communicationsession with a group consisting of one or more member devices in block1016, displaying a visual representation of the one or more members ofthe communication group at block 1018, and determining a participationstate of each member of the group in block 1020. The wirelesscommunication device 100 may determine the reason(s) fornon-participation for one or more non-participating group members inblock 1022. In various embodiments, the reasons for non-participationmay include that the particular member is busy, the member'scommunication device is unreachable, or the member's device is otherwiseunavailable, for example. The user's device 100 may display visualfeatures representing the participation state of each member of thegroup in block 1024. In various embodiments, the user's device 100 mayreceive a request from the user on a user interface to display one ormore reason(s) for non-participation by the one or morenon-participating group members in optional block 1028. The request todisplay the reason(s) for non-participation may be made by clicking onan icon of a non-participating member, for example. In response to therequest, the device 100 may display on a display screen 104 thereason(s) for non-participation in block 1028. In some embodiments, theoptional block 1028 may be omitted, and the device 100 may automaticallydisplay the one or more reason(s) for non-participation in block 1028.When the participation state of one or more group members changes (i.e.,decision block 1030=Yes), then the device 100 may determine an updatedparticipation state in block 1020 and the reason for non-participationby any new non-participating members in block 1022, and may display theupdated participation status and reasons for non-participation in blocks1024 and 1028, respectively. Similarly, where a reason fornon-participation of one or more group members changes (i.e.,determination block 1032=Yes), then the device 100 may proceed to block1020 to update the participation state and reasons fornon-participation, and display the updated status and reasons at blocks1024 and 1028. This may continue (i.e., determination block 1034=No)until the group communication session is terminated (i.e., determinationblock 1034=Yes) in block 1036.

FIG. 10C is a process flow diagram illustrating an embodiment method1003 of operation of a server 310 in a group communication session. Insome embodiments, the method 1003 of FIG. 10 may be performed inconjunction with method 1000 and/or method 1001 of FIGS. 10A and 10B,respectively. The server 310 may receive a request to initiate a groupcommunication session sent from a wireless communication device in block1038. The server 310 may determine the participation state of eachmember of the group in block 1040. For non-participating group members,the server 310 may determine the reason(s) for non-participation inblock 1042. The server 310 may send a communication to at least oneparticipating group member device indicating the participation state ofat least one other group member and/or the reason(s) fornon-participation of at least one non-participating member at block1044. When the participation state of one or more group members changes(i.e., decision block 1046=Yes), or when a reason for non-participationchanges (i.e., decision block 1048=Yes), then the server 310 may proceedto block 1020 to determine the updated participation states and reasonsin block 1022, and may send a communication to at least oneparticipating group member to update the participation status and/orreasons for non-participation in block 1044. This may continue (i.e.,determination block 1050=No) until the group communication session isterminated (i.e., determination block 1050=Yes) in block 1052.

FIGS. 11A-D are screenshots of a touchscreen display 104 illustrating auser-actuated locking mechanism which may be used to lock control of thefloor in a group communication (e.g., PTT) enabled device 100 device for“hands-free” operation. In FIG. 11A, the display 104 includes a virtualPTT button 1102. In various embodiments, the virtual PTT button 1102 mayfunction much like a conventional hardware PTT button. When the device100 detects a touch event on the virtual button 1102, the device 100 maytransmit a request to the communication server 310 to open acommunication channel from the wireless device 100 to the otherdevice(s) in the PTT group. FIG. 11B illustrates the display screen 104showing that the user's finger 610 is touching the display screen 104and the floor has been granted to the user's device 100. As describedabove, the display screen 104 can use visual feedback, such as graphicalelements or color coding, to indicate to the user that the floor hasbeen granted.

In some embodiments, in a conventional mode of operation the device 100may maintain floor control while the device detects a touch event on thescreen 104 or on a portion thereof. Thus, the device may operate like aconventional PTT-enabled device having a dedicated PTT button in whichthe user must keep the PTT button pressed while communicating with thegroup. Thus, in order to communicate with the at least one other memberof the communication group, the user must maintain continuous touchcontact with the screen 104. It will be understood that even where theuser maintains touch contact with the screen, the user's device maystill lose control of the floor, where, for example, another device inthe group, having a higher priority than the original user's device asdetermined by server 310, simultaneously requests control of the floor.

In various embodiments, in addition to the conventional mode describedabove, the device 100 may additionally include a “hands-free” mode inwhich the user may actuate a locking mechanism to maintain control ofthe floor (i.e., “lock” the floor) without requiring the user tocontinuously maintain contact with the screen. The user actuated lockingmechanism may take a variety of forms, such as a virtual button on atouchscreen interface/display, or a key entry on a conventional keypadinterface. As shown in FIG. 11B, the locking mechanism 1104 may be asliding lock on a touchscreen display 104. The sliding lock may be a“target-based” lock, meaning that the user may actuate the lock bytouching the screen at a first location and then sliding his or herfinger 610 towards a second “target” location on the screen. The device100 may detect a touch event on the first location and the slidingmovement of the finger 610 towards the second “target” location. Whenthe device 100 detects the finger 610 within a pre-determined proximityto the target location, the device 100 may enter a “hands-free” mode, inwhich the device 100 maintains an open communication channel withoutrequiring continuous user contact with the user interface. In theexample shown in FIGS. 11A-B, the first location may be the virtual PTTbutton 1102 in FIG. 11A and the second, or “target” location may be the“slide to lock” bar 1104 in FIG. 11B. The user may actuate the“hands-free” mode by sliding his or her finger 610 from the virtual PTTbutton 1102 to the “slide to lock” bar 1104. This actuates the slidinglock mechanism. The device 100 may provide visual and/or audio feedbackof entry into the “hands-free” mode. For example, as shown in FIG. 11C,upon entry into the “hands-free” mode, the “slide to lock” bar 1104 maydisappear and a “slide to unlock” bar 1106 may be displayed in adifferent location. In various embodiments, the “hands-free” mode mayenable a user to maintain an open PTT communication channel withoutphysically contacting the user interface or even without holding thedevice. As shown in 11C, in the “hands free” mode, the device maymaintain control of the “floor” for group communication when the user'sfinger 610 is removed from the screen 104. The device 100 may utilize aspeakerphone option. In certain embodiments, as shown in FIG. 11D, thehands-free mode may be used in conjunction with an earpiece device 1110,such as a headset, which may be connected to the device 100 via asuitable link, which may be a wireless link 1108, such as a BLUETOOTH®wireless link.

The device 100 may remain in hands-free mode until either the device 100loses floor control (e.g., the server 301 grants control of the floor toanother device based on server floor arbitration priority rules), or theuser actuates an unlocking mechanism. In various embodiments, theunlocking mechanism may be the same mechanism as the locking mechanism,and the user may toggle between a locked and an unlocked state. Thus, tode-activate the locking mechanism the user may slide the lockingmechanism (e.g., a virtual display on a touchscreen interface) in theopposite direction as the locking movement in order to de-activate thelocking mechanism. The unlocking mechanism may be a virtual button on atouchscreen interface/display, or a key entry on a conventional keypadinterface. As shown in FIG. 11C, the unlocking mechanism 1106 may be asliding lock on a touchscreen display 104. The sliding lock may be a“target-based” lock, as described above. In the example shown in FIG.11C, the user may touch a first location, which may be in the centralregion of the display 104 and slide his or her finger to a “target”location, which may be the “slide to unlock” bar 1106. When the device100 detects the user's finger within a pre-determined proximity of the“slide to unlock” bar 1106, the device may exit the “hands-free” mode,de-activate the lock mechanism and return to a conventional mode ofoperation.

FIG. 12A is a process flow diagram illustrating an embodiment method1200 of group communication, such as PTT communication, with a wirelesscommunication device 100 using a “hands-free” mode. The device 100 maybegin a group communication session in block 1202 and determine a stateof the group communication in block 1203. The device 100 may display, ona display screen 104, the state of the group communication session usingvisual feedback in block 1204. The device 100 may receive user input ona user interface to initiate a group communication in block 1206. Theuser input may be a touch event on a touchscreen, such as a touch eventon a virtual PTT button, as described above in connection with FIGS.11A-D. In other embodiments, the user input may be a key entry on akeypad interface. The device 100 may send a request to a server, such ascommunication server 310, for control of the “floor” in a groupcommunication session in block 1208. If control of the floor is notgranted (i.e., determination block 1210=No), then the device may proceedto block 1203 to determine the state of the group communication. Whencontrol of the floor is granted (i.e., determination block 1210=Yes),then the device 100 may establish an open group communication channelwith one or more devices in a communication group in block 1212. Thedevice 100 may display visual feedback on the display screen 104indicating a group communication state of floor granted to the user'sdevice in block 1214.

The device may display an indication that the user has the ability tolock the floor in block 1215. This may include displaying a lockingmechanism on the screen, such as the “slide-to-lock” indication in FIG.11B. The device 100 may detect the actuation of a locking mechanism bythe user on the user interface in block 1216. In various embodiments,the user-actuated locking mechanism may be, for example, a virtualbutton on a touchscreen interface/display, or a key entry on aconventional keypad interface. In some embodiments, such as shown inFIGS. 11A-D, the locking mechanism 1104 may be a sliding lock on atouchscreen display 104. The sliding lock may be a “target-based” lock,meaning that the user may actuate the lock by touching the screen at afirst location and then sliding his or her finger towards a second“target” location on the screen.

While the locking mechanism is actuated, the device 100 may maintain theopen group communication channel in a “hands-free” mode in block 1218.As described above, the “hands-free” mode of the device 100 may enablethe device to maintain control of the floor (i.e., “lock” the floor)without requiring the user to continuously maintain contact with theuser interface, as is the case in conventional PTT-enabled devices. Thedevice 100 may provide an indication of a group communication state offloor locked to the user's device in block 1220. For example, the device100 may provide audio feedback and/or display visual feedback on displayscreen 104 to indicate that the floor is locked to the user's device in“hands-free” mode. The device 100 may remain in “hands-free” mode whilethe locking mechanism remains actuated (i.e., determination block1222=Yes). The user may unlock the device 100 by actuating an unlockingmechanism, which in various embodiments may be the same as the lockingmechanism, may involve de-activating the locking mechanism by moving theindication in the opposite direction to locking, and may be a virtualbutton on a touchscreen interface or a key entry on a keypad interface.As shown in FIGS. 11A-D, the unlocking mechanism 1106 may be a slidinglock on a touchscreen display 104. The sliding lock may be a“target-based” lock, meaning that the user may unlock the device bytouching the screen at a first location and then sliding his or herfinger towards a second “target” location on the screen.

When the locking mechanism is de-activated or no longer actuated (i.e.,determination block 1222=No), the device 100 may end the “hands-free”mode and provide an indication that the floor is no longer locked to theuser's device in block 1224. The device 100 may continue the groupcommunication (i.e., determination block 1227=Yes), and maintain thecommunication channel in response to user input (such as the usercontinuing to contact the touchscreen) in block 1229, or the device maynot continue the communication (i.e., determination block 1227=No) andclose the communication channel in block 1231. In various embodiments, alocking mechanism such as described above in connection with FIGS. 11A-Dand 12 may be used to initiate other PTT modes, in alternative to or inaddition to the “hands-free” mode described above. In some embodiments,the device 100 may include a plurality of user-actuated lockingmechanisms, which may be, for example, virtual buttons on a touchscreeninterface/display, and/or key entries on a conventional keypadinterface. In some embodiments, the device 100 may include a slidinglock on a touchscreen display 104, such as shown in FIGS. 11A-D. Thesliding lock may be a “target-based” lock having a plurality ofdifferent “target” locations on the screen. The user may actuate andde-actuate different locks by touching the screen at a first locationand then sliding his or her finger towards the different “target”locations on the screen. The different target locations may correspondwith different PTT modes, according to various embodiments.

FIG. 13A is a process flow diagram illustrating an embodiment method1300 of group communication, such as PTT communication, with a wirelesscommunication device 100 using a “priority lock” mode. The priority lockmode may be utilized when the user desires priority access to the“floor” in a group communication. In various embodiments, the initiationof the “priority lock” mode may provide the device with uninterruptedcontrol of the floor in a group communication while the priority lock isactuated. In various embodiments, the initiation of the priority lock bythe user's device may temporarily alter the priority rules used by aserver 310 in arbitrating between different devices in a group forcontrol of the floor. In various embodiments, the priority lock mode maybe used to provide a device 100 with a higher priority status at theserver 310 when arbitrating between competing requests for the floorthan the priority status of the device 100 when the device not inpriority lock mode.

In the embodiment method 1300 shown in FIG. 13A, the device 100 maydetermine the state of a group communication session in block 1302. Thedevice 100 may display, on a display screen 104, a state of the groupsession using visual feedback in block 1304. The device 100 may receiveuser input on a user interface to initiate a group communication inblock 1306. The user input may be a touch event on a touchscreen, suchas a touch event on a virtual PTT button, as described above inconnection with FIGS. 11A-D. In other embodiments, the user input may bea key entry on a keypad interface. The device 100 may send a request toa server, such as communication server 310, for control of the “floor”in a group communication session in block 1308. If control of the flooris not granted (i.e., determination block 1310=No), then the device maydetermine the updated state of the group communication in block 1302 anddisplay the updated state in block 1304. When control of the floor isgranted (i.e., determination block 1310=Yes), then the device 100 mayestablish an open group communication channel with one or more devicesin a group in block 1312. The device 100 may display visual feedback onthe display screen 104 indicating a group communication state of floorgranted to the user's device in block 1314. The device 100 may furtherprovide an indication to the user that a priority locked mode isavailable.

The device 100 may detect the actuation of a priority locking mechanismby the user on the user interface in block 1316. In various embodiments,the user-actuated locking mechanism may be, for example, a virtualbutton on a touchscreen interface/display, or a key entry on aconventional keypad interface. In some embodiments, the lockingmechanism may be a sliding lock on a touchscreen display 104, such asthe sliding locking mechanism shown in FIGS. 11A-D. The sliding lock maybe a “target-based” lock, meaning that the user may actuate the lock bytouching the screen at a first location and then sliding his or herfinger towards a second “target” location on the screen. In variousembodiments, the sliding lock may include a plurality of targetlocations on the display screen, where each target location initiates adifferent group communication mode of the device. For example, a firsttarget location may correspond with a “priority lock” mode, and a secondtarget location may correspond with another mode, such as the“hands-free” mode described above in connection with FIG. 12.

Upon detection of a user actuation of the priority locking mechanism inblock 1316, the device 100 may send a request to a server, such ascommunication server 310, for priority floor access at block 1318. Ifthe request is not granted (i.e., determination block 1320=No), thedevice 100 may then communicate over the group communication channel ina non-priority locked mode in block 1332. When the request is granted(i.e., determination block 1320=Yes), the device 100 may maintain thegroup communication channel in “priority locked” mode in block 1322 anddisplay a state of floor priority locked on user's device 100 in block1324. In various embodiments, the priority lock mode may provide thedevice 100 with control of the floor which generally may not beinterrupted by another device in the group. While the priority lockingmechanism is activated (i.e., determination block 1326=Yes), the devicemay maintain the group communication channel in a “priority lock” modein block 1322. When the priority locking mechanism is no longer actuated(i.e., determination block 1326=No), then the device 100 may end thepriority lock mode and provide an indication that the floor is no longerpriority locked in block 1328. The device 100 may notify the server 310that priority floor access is no longer requested at block 1330. Thedevice 100 may continue to communicate over the group communicationchannel in a non-priority locked mode in block 1332.

In some embodiments, priority locking mechanism may allow the user tolock the device to one of a plurality of different priority levels. Thismay be similar to an automotive transmission gearshift, in which thedifferent priority levels are analogous to the different gears (e.g.,first gear, second gear, third gear, etc.) of a gearshift. A firstpriority locking level may provide a first level of priority access forfloor control, a second priority level may provide a second,progressively higher level of priority access for floor control, and soforth. The various priority levels may be actuated using a target-basedsliding lock mechanism, such as described above, where the user may usethe locking mechanism to actuate progressive levels of priority locking.

FIG. 13B is a process flow diagram illustrating an embodiment method1301 of operation of a server 310 in a group communication session, suchas a PTT communication session, in which a user device requests priorityfloor access. In some embodiments, the method 1301 of FIG. 13B may beperformed in conjunction with method 1300 of FIG. 13A. The server 310may receive a request for priority floor access from a first user device100 in block 1334. The server 310 may determine whether to grant or denythe request at determination block 1336. The server 310 may deny therequest (i.e., determination block 1336=“No”), for example, if thepriority locking feature is not authorized or otherwise not availablefor the requesting user device 100. The server 310 may then send amessage to the first user device 100 that the request for priority flooraccess is denied in block 1346, and arbitrate floor control of the groupcommunication session in accordance with the normal priority rules(i.e., without providing priority access to the first user device 100)in block 1344. If the server 310 grants the request for priority flooraccess (i.e., determination block 1336=“Yes”), then the server 310 maysend a message to the first user device 100 indicating that priorityfloor access is granted in block 1338. In block 1340, the server 310 mayarbitrate floor control of the group communication session with priorityfloor access being given to the first user device 100. In variousembodiments, the server 310 may give priority floor access byimmediately granting the floor to the first user device 100, regardlessof whether another device currently has the floor, and may grant thefirst user device 100 uninterrupted control of the floor until the firstuser device 100 indicates that priority floor access is no longerrequested. The server 310 may receive a message from the first userdevice 100 that priority floor access is no longer requested at block1342. The server 310 may then arbitrate floor control of the groupcommunication session in accordance with the normal priority rules(i.e., without providing priority access to the first user device 100)in block 1344.

In various embodiments, the server 310 may grant priority floor accessto a user device for a pre-determined maximum time period, and if nomessage is received from the user device 100 within that time period,the server 310 may release the user device 100 from priority flooraccess. The server 310 may also implement priority rule(s) for handlingfloor control in cases where more than one user device requests priorityfloor access at the same time.

FIG. 14A is a process flow diagram illustrating an embodiment method1400 of group communication, such as PTT communication, with a wirelesscommunication device 100 using a “media lock” mode. The media lock modemay be utilized when the user desires priority access to the “floor” fortransmitting media file(s) to one or more members of a group in a groupcommunication, while still enabling other devices to transmit voice datato the group. The media files may include, for example, image files,video files, audio files, documents and presentations, and the like. Incertain embodiments, the initiation of the “media lock” mode may providethe device with uninterrupted control of the floor for transmitting amedia file in a group communication while the media lock is actuated. Invarious embodiments, the initiation of the media lock by the user'sdevice may temporarily alter the priority rules used by a server 310 inarbitrating floor control for transmitting media files between differentdevices in a communication group.

In the embodiment method 1400 shown in FIG. 14A, the device 100 maydetermine a state of a group communication session in block 1402, anddisplay, on a display screen 104, the determined state of the groupcommunication session using visual feedback in block 1404. The device100 may detect the actuation of a media locking mechanism by the user onthe user interface in block 1406. In various embodiments, theuser-actuated media locking mechanism may be, for example, a virtualbutton on a touchscreen interface/display, or a key entry on aconventional keypad interface. In some embodiments, the media lockingmechanism may be a sliding lock on a touchscreen display 104, such asthe sliding locking mechanism shown in FIGS. 11A-D. The sliding lock maybe a “target-based” lock, meaning that the user may actuate the lock bytouching the screen at a first location and then sliding his or herfinger towards a second “target” location on the screen. In variousembodiments, the sliding lock may include a plurality of targetlocations on the display screen, where each target location initiates adifferent group communication mode of the device. For example, a firsttarget location may correspond with a “media lock” mode, and one or moreadditional target location(s) may correspond with another mode, such asthe “hands-free” mode described above in connection with FIG. 12 and/orthe “priority lock” mode described above in connection with FIG. 13A.

Upon detection of a user actuation of the media locking mechanism inblock 1406, the device 100 may send a request to a server, such ascommunication server 310, for a media lock at block 1408. If the requestis not granted (i.e., determination block 1410=No), the device 100 maytransmit media in the normal manner over a non-“media-locked” channel inblock 1428. When the request is granted (i.e., determination block1410=Yes), the device 100 may establish a group media communicationchannel in block 1412, and maintain the group media communicationchannel in “media locked” mode in block 1414. The device 100 may displayon the display screen 104 visual features indicating a groupcommunication state of media lock granted in block 1416. While the medialocking mechanism is actuated (i.e., determination block 1418=Yes), thedevice 100 may maintain the group media communication channel in a medialocked mode in block 1414. When the media locking mechanism is no longeractuated (i.e., determination block 1418=No), then the device 100 maysend a message to the server 310 to end the media lock at block 1422.The device 100 may discontinue the media communication (i.e.,determination block 1424=No), and close the group media communicationchannel in block 1426. The device may alternatively continue the mediacommunication (i.e., determination block 1424=Yes) and transmit themedia over a non-“media locked” channel in block 1428.

FIG. 14B is a process flow diagram illustrating an embodiment method1401 of operation of a server 310 in a group communication session, suchas a PTT communication session, in which a user device requests a “medialock” for transmission of media file(s). In some embodiments, the method1401 of FIG. 14B may be performed in conjunction with method 1400 ofFIG. 14A. The server 310 may receive a request for a media lock from afirst user device 100 in block 1430. The server 310 may determinewhether to grant or deny the request at determination block 1432. Theserver 310 may deny the request (i.e., determination block 1432=No), forexample, if the media lock feature is not authorized or is otherwise notavailable for the requesting user device 100. The server 310 may thensend a message to the first user device 100 that the request for a medialock is denied in block 1442, and arbitrate floor control of the groupcommunication session for transmission of media files using the normalpriority rules (i.e., without providing a media lock to the first userdevice 100) in block 1440. If the server 310 grants the request forpriority floor access (i.e., determination block 1432=Yes), then theserver 310 may send a message to the first user device 100 indicatingthat priority floor access is granted in block 1434. In block 1336, theserver 310 may lock control of the floor for transmission of mediafile(s) to the first user's device 100. In various embodiments, whilethe floor is “locked” to the first user's device 100 for transmission ofmedia files, the server 310 may still arbitrate control of the floor forvoice communication between the various user devices in thecommunication group. The server 310 may receive a message from the firstuser device 100 that the media lock is no longer requested at block1438. The server 310 may then arbitrate floor control for transmissionof media files in accordance with the normal priority rules (i.e.,without providing a media lock to the first user device 100) in block1440.

In various embodiments, the server 310 may grant a media lock to a userdevice 100 for a pre-determined maximum time period, and if no messageis received from the user device 100 within that time period, the server310 may release the media lock. The server 310 may also implementpriority rule(s) for handling floor control in cases where more than oneuser device requests a media lock at the same time.

FIG. 15A is a process flow diagram illustrating an embodiment method1205 of PTT communication with a wireless communication device 100 usinga “lockout” mode. The lockout mode may be utilized to enable the user totemporarily exclude one or more members of the group communication groupfrom receiving communications from the user's device 100 during a groupcommunication session.

In the embodiment method 1500 shown in FIG. 15A, the device 100 maybegin a group communication session, such as a PTT communication, inblock 1502. The device 100 may display, on a display screen 104, a stateof the group communication session using visual feedback in block 1504.The device 100 may detect the actuation of a lockout mechanism by theuser on the user interface in block 1506. In various embodiments, theuser-actuated lockout mechanism may be, for example, a virtual button ona touchscreen interface/display, or a key entry on a conventional keypadinterface. In some embodiments, the media locking mechanism may be asliding lock on a touchscreen display 104, such as the sliding lockingmechanism shown in FIGS. 11A-D. The sliding lock may be a “target-based”lock, meaning that the user may actuate the lock by touching the screenat a first location and then sliding his or her finger towards a second“target” location on the screen. In various embodiments, the slidinglock may include a plurality of target locations on the display screen,where each target location initiates a different group communicationmode of the device. For example, a first target location may correspondwith a “lockout” mode, and one or more additional target location(s) maycorrespond with another group communication mode, such as the“hands-free” mode described above in connection with FIG. 12, the“priority lock” mode described above in connection with FIG. 13A and/orthe “media lock” mode described above in connection with FIG. 14A.

In various embodiments, the user may select one or more members of thegroup with which to “lock out” from group communications. The user may,for example, select a contact icon representing a particular groupmember and actuate the lockout mechanism to lock out the group memberfrom group communications. In some embodiments, the contact icon of thegroup member to be locked out may be the “target” in a target-basedsliding lock mechanism. The user may slide his or her finger toparticular contact icon(s) to lock out the respective user(s) from groupcommunication. In some embodiments, the user may drag the contact iconsto an additional target location, such as a “lockout” icon, toeffectuate the lockout mode with respect to that group member. In otherembodiments, the device 100 may display a locking mechanism (e.g., aslide-to-lock bar, a “virtual” switch, toggle, button, etc.) inassociation with each contact icon. The locking mechanism may bedisplayed, for example, after the user first touches the contact icon.Actuating the locking mechanism may effectuate the lockout mode withrespect to the selected group member.

Upon detection of the user actuation of the lockout mechanism in block1506, the device 100 may establish a group communication channel withone or more devices in the group, excluding device(s) of locked-outgroup member(s) in block 1508. This may involve a temporaryreconfiguring of the group communication session, which may be performedby, or in conjunction with, a group communication server 310, asdiscussed below. The user device 100 may exclude the device(s) oflocked-out group member(s) from outgoing group communications in block1510. The device 100 may display on the display screen 104 visualfeatures indicating that a lockout is actuated with respect to selectedgroup member(s) in block 1512. While the lockout is actuated (i.e.,determination block 1514=Yes), the device 100 may continue to excludethe device(s) of locked out group member(s) from outgoing groupcommunications from the user's device 100 in block 1510. When thelockout mechanism is no longer actuated (i.e., determination block1514=No), then the device 100 may include the device(s) of previouslylocked out group member(s) in outgoing group communications in block1516. In other words, the group communication session may be returned toits original configuration.

FIG. 15B is a process flow diagram illustrating an embodiment method1501 of operation of a server 310 in a group communication session, suchas a PTT communication session, in which a lockout mechanism isactivated on a user device with respect to at least one other userdevice in the communication group. In some embodiments, the method 1501of FIG. 15B may be performed in conjunction with method 1500 of FIG.15A. In block 1518, the server 310 may configure a group communicationsession between a plurality of user devices in a normal manner. Theserver 310 may receive an indication from a first user device 100 that alockout mechanism has been actuated with respect to at least one seconduser device in the communication group in block 1520. The server 310 may(temporarily) reconfigure the group communication session to excludecommunications from the first user device 100 from being received by the“locked out” devices at block 1522. The server 310 may maintain thisreconfigured group communication session (block 1526) until the server310 receives an indication from the first user device 100 that thelockout is no longer actuated with respect to the at least one seconduser device in block 1526. The server 310 may return to the initialconfiguration of the group communication session in block 1528.

FIG. 16A is a process flow diagram illustrating an embodiment method1600 of group communication, such as PTT communication, with a wirelesscommunication device 100 using a “blocking” mode. The blocking mode maybe utilized to enable the user to temporarily block the user's device100 from receiving communications from the device(s) of one or moreselected members of the group communication group during a groupcommunication session.

In the embodiment method 1600 shown in FIG. 16A, the device 100 maybegin a group communication session in block 1602. The device 100 maydisplay, on a display screen 104, a state of the group session usingvisual feedback in block 1604. The device 100 may detect the actuationof a blocking mechanism by the user on the user interface in block 1606.In various embodiments, the user-actuated blocking mechanism may be, forexample, a virtual button on a touchscreen interface/display, or a keyentry on a conventional keypad interface. In some embodiments, the medialocking mechanism may be a sliding lock on a touchscreen display 104,such as the sliding locking mechanism shown in FIGS. 11A-C. The slidinglock may be a “target-based” lock, meaning that the user may actuate thelock by touching the screen at a first location and then sliding his orher finger towards a second “target” location on the screen. In variousembodiments, the sliding lock may include a plurality of targetlocations on the display screen, where each target location initiates adifferent group communication mode of the device. For example, a firsttarget location may correspond with a “blocking” mode, and one or moreadditional target location(s) may correspond with another mode, such asthe “hands-free” mode described above in connection with FIG. 12, the“priority lock” mode described above in connection with FIG. 13A, the“media lock” mode described above in connection with FIG. 14A, and/orthe “lockout” mode described above in connection with FIG. 15A.

In various embodiments, the user may select one or more members of thegroup to “block” from receiving group communications by the user'sdevice 100. The user may, for example, select a contact iconrepresenting a particular group member and actuate the blockingmechanism to block communications from the selected group member. Insome embodiments, the contact icon of the group member to be blocked maybe the “target” in a target-based sliding lock mechanism. The user mayslide his or her finger to particular contact icon(s) to block therespective user(s). In some embodiments, the user may drag the contacticon of a particular group member to a target area, such as a “block”icon, to effectuate the block. In other embodiments, the device 100 maydisplay a locking mechanism (e.g., a slide-to-lock bar, a “virtual”switch, toggle or button, etc.) in association with each contact icon.The blocking mechanism may be displayed, for example, after the userfirst touches the contact icon. Actuating the blocking mechanism mayeffectuate a block of the selected group member.

Upon detecting a user actuation of the blocking mechanism in block 1606,the device 100 may block communications from selected blocked groupmember(s) from being received by the user's device 100 in block 1608.The device 100 may display on the display screen 104 visual featuresindicating that blocking is actuated with respect to selected groupmember(s) in block 1610. While the blocking is actuated (i.e.,determination block 1612=Yes), the device 100 may continue to blockcommunications from the blocked member(s) in block 1608. When theblocking mechanism is no longer actuated (i.e., determination block1612=No), then the device 100 may receive communications from previouslyblocked group members in block 1614.

In some embodiments, the blocking mode may be analogous to a “mute”button, in that the user does not hear or view communications from theblocked group member(s), but other users in the group may still receivecommunications from the blocked member(s). In some embodiments, theblocking function may be implemented on the user device 100 without theknowledge or intervention of a server. In other embodiments, the userdevice 100 may signal a server, such as group communication server 310,when the blocking mechanism is actuated, and the server 310 mayreconfigure the communication session so that communications from ablocked device are not transmitted to the blocking device 100. In someembodiments, actuating the blocking mechanism with respect to a groupmember's device may block the selected device from sending anycommunications to the group (e.g., it may prevent the blocked devicefrom gaining control of the “floor”). In this embodiment, upon actuationof the blocking mechanism, the device 100 may send a request to aserver, such as group communication server 310, to block a specifieddevice from communicating with the group. The server 310 may determinewhether to block the device based on pre-determined blocking criteriawhich may be stored at the server 301, and which may include, forexample, the priority status of the user requesting the block, thepriority status of the user requested to be blocked, the number ofdifferent blocking requests received for a particular user, etc.

FIG. 16B is a process flow diagram illustrating an embodiment method1601 of operation of a server 310 in a group communication session, suchas a PTT communication session, in which a blocking mechanism isactivated on a user device with respect to at least one other userdevice in the communication group. In some embodiments, the method 1601of FIG. 16B may be performed in conjunction with method 1600 of FIG.16A. In block 1616, the server 310 may configure a group communicationsession between a plurality of user devices in a normal manner. Theserver 310 may receive an indication from a first user device 100 that ablocking mechanism has been actuated with respect to at least one seconduser device (i.e., a “blocked” device) in the communication group inblock 1618. The server 310 may (temporarily) reconfigure the groupcommunication session to exclude communications from the “blocked”device(s) from being received at first user device 100 in block 1620. Asdiscussed above, in various embodiments the server 310 may reconfigurethe group communication session such that communications from a“blocked” device are not received at any other devices in thecommunication group. The server 310 may maintain this reconfigured groupcommunication session (block 1622) until the server 310 receives anindication from the first user device 100 that the blocking mechanism isno longer actuated with respect to the at least one second user devicein block 1624. The server 310 may return to the initial configuration ofthe group communication session in block 1626.

FIGS. 17A-C are screenshots of a touchscreen display 104 of a wirelesscommunication device 100 having a “quick contact” PTT shortcut on adesktop/home screen of the device 100. As shown in FIG. 17A, the device100 may enable the user to display one or more shortcut icons 1704 to aPTT contact on the home screen 1702. The PTT contact may be anindividual PTT user or a group of PTT users. Selection of the shortcuticon 1704 may bring up a modified PTT button 1706, as shown in FIG. 17B.The device 100 may detect a touch event on the PTT button 1706, and inresponse, establish a PTT communication channel with the device of thecontact shown in icon 1704. As shown in FIG. 17C, the modified PTTbutton may also support the slide to lock feature 1708 in certainembodiments. The slide to lock feature 1708 may initiate a “hands free”mode of operation and/or any of the operating modes described above inconnection with FIGS. 12-16B. This is an improvement over existingnon-dedicated hardware solutions in that the user does not need tofind/launch/navigate the PTT application in order to quickly speak totheir contact.

FIG. 18A is a process flow diagram illustrating an embodiment method1800 for group communication, such as PTT communication, using a “quickcontact” shortcut. A wireless communication device 100 may display atleast one quick contact group communication shortcut icon on the homescreen of the device display 104 in block 1806. The display 104 may be atouchscreen display. The quick contact shortcut icon(s) may be set up bythe user, or can be automatically generated by the device 100 based on,for example, contact information stored on the device.

The device 100 may detect a user selection of a quick contact groupcommunication shortcut icon on a user interface in optional block 1806,and may display a group communication button (e.g., a PTT button) inassociation with the quick contact shortcut icon in step 1808. In someembodiments, the optional step 1806 may be omitted, and the device 100may automatically display the group communication button in associationwith the quick contact shortcut icon in step 1808. In some embodiments,the group communication button may comprise a portion of or the entiretyof the quick connect group communication shortcut icon. The device 100may detect a selection of the group communication button by a user on auser interface in block 1808. In various embodiments using a touchscreendisplay, the device 100 may detect a touch event on the groupcommunication button. The device 100 may initiate a group communicationwith the device of the selected contact in block 1810.

FIG. 18B is a process flow diagram illustrating an embodiment method1801 for group communication, such as PTT communication, using a “quickcontact” shortcut and a sliding locking mechanism. Blocks 1812-1816 aresimilar to blocks 1802-1806 of method 1800 shown in FIG. 18A, andinclude displaying at least one quick contact group communicationshortcut icon on the home screen of a wireless communication devicedisplay 100 in block 1812, detecting a selection of a quick contactgroup communication shortcut icon by a user on a user interface inoptional block 1814, and displaying a group communication button (e.g.,a PTT button) in association with the quick contact group communicationshortcut icon in block 1816. The device 100 may detect the actuation ofa locking mechanism by the user on the user interface in block 1820. Thelocking mechanism may be a sliding lock that is displayed in response touser selection of the group communication button, such as shown in FIGS.17A-C. Actuation of the sliding lock may initiate a “hands-free” mode ofoperation. The device 100 may initiate group communication with thedevice of the selected contact in “hands free” mode in block 1822. Inalternative embodiments, the sliding lock mechanism may initiate any ofthe operating modes described above in connection with FIGS. 12-16B.

FIG. 19 is a system block diagram of a wireless communication device foruse with any of the embodiments. The embodiments may be implemented in avariety of mobile wireless communication devices, particularly mobilecomputing devices. An example of a wireless communication device thatmay implement the various embodiments is a Smartphone 2800 illustratedin FIG. 19. A wireless communication device, such as a Smartphone 2800,may include a processor 2801 coupled to memory 2802 and to a radiofrequency data modem 2805. The modem 2805 may be coupled to an antenna2804 for receiving and transmitting radio frequency signals. TheSmartphone 2800 may also include a display 2803, such as a touch screendisplay. The mobile device 2800 may also include user input devices,such as buttons 2806, to receive user inputs. In the various embodimentsthe Smartphone 2800 includes a tactile output surface, which may bepositioned on the display 2803 (e.g., using E-Sense™ technology), on aback surface 2812, or another surface of the mobile device 2800. Themobile device processor 2801 may be any programmable microprocessor,microcomputer or multiple processor chip or chips that can be configuredby software instructions (applications) to perform a variety offunctions, including the functions of the various embodiments describedherein. Typically, software applications may be stored in the internalmemory 2802 before they are accessed and loaded into the processor 2801.In some mobile computing devices, additional memory chips (e.g., aSecure Data (SD) card) may be plugged into the mobile device and coupledto the processor 2801. The internal memory 2802 may be a volatile ornonvolatile memory, such as flash memory, or a mixture of both. For thepurposes of this description, a general reference to memory refers toall memory accessible by the processor 2801, including internal memory2802, removable memory plugged into the mobile device, and memory withinthe processor 2801.

The various embodiments may be implemented on any of a variety ofcommercially available server devices, such as the server 2900illustrated in FIG. 20. Such a server 2900 typically includes aprocessor 2901 coupled to volatile memory 2902 and a large capacitynonvolatile memory, such as a disk drive 2903. The server 2900 may alsoinclude a floppy disc drive, compact disc (CD) or DVD disc drive 2906coupled to the processor 2901. The server 2900 may also include networkaccess ports 2904 coupled to the processor 2901 for establishing dataconnections with a network 2905, such as a local area network coupled toother broadcast system computers and servers. The processors 2801, 2901may be any programmable microprocessor, microcomputer or multipleprocessor chip or chips that can be configured by software instructions(applications) to perform a variety of functions, including thefunctions of the various embodiments described above. In some devices,multiple processors 2801, 2901 may be provided, such as one processordedicated to wireless communication functions and one processordedicated to running other applications. Typically, softwareapplications may be stored in the internal memory 2802, 2902, and 2903before they are accessed and loaded into the processor 2801, 2901.

The processor 2801, 2901 may include internal memory sufficient to storethe application software instructions. In many devices the internalmemory may be a volatile or nonvolatile memory, such as flash memory, ora mixture of both. For the purposes of this description, a generalreference to memory refers to memory accessible by the processor 2801,2901 including internal memory or removable memory plugged into thedevice and memory within the processor 2801, 2901 itself.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the steps of the various embodiments must be performed inthe order presented. As will be appreciated by one of skill in the artthe order of steps in the foregoing embodiments may be performed in anyorder. Words such as “thereafter,” “then,” “next,” etc. are not intendedto limit the order of the steps; these words are simply used to guidethe reader through the description of the methods. Further, anyreference to claim elements in the singular, for example, using thearticles “a,” “an” or “the” is not to be construed as limiting theelement to the singular.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the aspects disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with the aspectsdisclosed herein may be implemented or performed with a general purposeprocessor, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor maybe a microprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Alternatively, some steps ormethods may be performed by circuitry that is specific to a givenfunction.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on as one ormore instructions or code on a non-transitory computer-readable storagemedium. The steps of a method or algorithm disclosed herein may beembodied in a processor-executable software module which may reside orbe stored on a non-transitory computer-readable storage medium orprocessor-readable medium. Non-transitory computer-readable andprocessor-readable storage media may be any available media that may beaccessed by a computer or processor. By way of example, and notlimitation, such non-transitory computer-readable media may include RAM,ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storageor other magnetic storage devices, or any other medium that may be usedto store desired program code in the form of instructions or datastructures and that may be accessed by a computer. Disk and disc, asused herein, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and blu-ray disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of non-transitory computer-readable media.Additionally, the operations of a method or algorithm may reside as oneor any combination or set of codes and/or instructions on anon-transitory processor-readable medium and/or computer-readablemedium, which may be incorporated into a computer program product.

The preceding description of the disclosed aspects is provided to enableany person skilled in the art to make or use the present invention.Various modifications to these aspects will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other aspects without departing from the scope of theinvention. Thus, the present invention is not intended to be limited tothe aspects shown herein but is to be accorded the widest scopeconsistent with the principles and novel features disclosed herein.

What is claimed is:
 1. A method of conducting a group communicationsession on a wireless communication device, comprising: displaying aquick contact group communication shortcut icon on a home screen of adisplay of the wireless communication device; displaying a groupcommunication button in association with the quick contact groupcommunication shortcut icon on the home screen of the display; detectinga selection of the group communication button by a user on a userinterface; and initiating a group communication session with a device ofa contact associated with the quick contact group communication shortcuticon.
 2. The method of claim 1, wherein the group communication sessioncomprises a “Push-To-Talk” (PTT) communication.
 3. The method of claim1, wherein the device includes a touchscreen user interface display. 4.The method of claim 3, further comprising: displaying a lockingmechanism in association with the quick contact group communicationshortcut icon.
 5. The method of claim 4, wherein the locking mechanismcomprises a target-based sliding lock mechanism on a touchscreen userinterface display.
 6. A wireless communication device, comprising: adisplay; a memory; and a processor coupled to the display and to thememory and configured with processor-executable instructions to performoperations comprising: displaying a quick contact group communicationshortcut icon on a home screen of the display; displaying a groupcommunication button in association with the quick contact groupcommunication shortcut icon on the home screen of the display; detectinga selection of the group communication button by a user on a userinterface; and initiating a group communication session with a device ofa contact associated with the quick contact group communication shortcuticon.
 7. The wireless communication device of claim 6, wherein the groupcommunication session comprises a “Push-To-Talk” (PTT) communication. 8.The wireless communication device of claim 6, wherein the displaycomprises a touchscreen user interface display.
 9. The wirelesscommunication device of claim 8, wherein the processor is configuredwith processor-executable instructions to perform operations furthercomprising: displaying a locking mechanism in association with the quickcontact group communication shortcut icon.
 10. The wirelesscommunication device of claim 9, wherein the locking mechanism comprisesa target-based sliding lock mechanism implemented on a touchscreen userinterface display.
 11. A wireless communication device, comprising:means for displaying a quick contact group communication shortcut iconon a home screen of a display; means for displaying a groupcommunication button in association with the quick contact groupcommunication shortcut icon on the home screen of the display; means fordetecting a selection of the group communication button by a user on auser interface; and means for initiating a group communication sessionwith a device of contact associated with the quick contact groupcommunication shortcut icon.
 12. The wireless communication device ofclaim 11, wherein the group communication session comprises a“Push-To-Talk” (PTT) communication.
 13. The wireless communicationdevice of claim 11, wherein the device includes a touchscreen userinterface display.
 14. The wireless communication device of claim 13,further comprising: means for displaying a locking mechanism inassociation with the quick contact group communication shortcut icon.15. The wireless communication device of claim 14, wherein the lockingmechanism comprises a target-based sliding lock mechanism on atouchscreen user interface display.
 16. A non-transitorycomputer-readable storage medium having stored thereon processorexecutable instructions configured to cause a wireless communicationdevice processor to perform operations comprising: displaying a quickcontact group communication shortcut icon on a home screen of a displayof a wireless communication device; displaying a group communicationbutton in association with the quick contact group communicationshortcut icon on the home screen of the display; detecting a selectionof the group communication button by a user on a user interface; andinitiating a group communication session with a device of a contactassociated with the quick contact group communication shortcut icon. 17.The non-transitory computer-readable storage medium of claim 16, whereinthe stored processor executable instructions are configured to cause thewireless communication device processor to perform operations such thatthe group communication session comprises a “Push-To-Talk” (PTT)communication.
 18. The non-transitory computer-readable storage mediumof claim 16, wherein the stored processor executable instructions areconfigured to cause the wireless communication device processor toperform operations such that the device includes a touchscreen userinterface display.
 19. The non-transitory computer-readable storagemedium of claim 18, wherein the stored processor executable instructionsare configured to cause the wireless communication device processor toperform operations further comprising: displaying a locking mechanism inassociation with the quick contact group communication shortcut icon.20. The non-transitory computer-readable storage medium of claim 19,wherein the stored processor executable instructions are configured tocause the wireless communication device processor to perform operationssuch that the locking mechanism comprises a target-based sliding lockmechanism on a touchscreen user interface display.